-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(dashboard): Nv 4800 implement arrays and nested forms in custom step controls #7127
base: next
Are you sure you want to change the base?
feat(dashboard): Nv 4800 implement arrays and nested forms in custom step controls #7127
Conversation
✅ Deploy Preview for novu-stg-vite-dashboard-poc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for the Array went with the UI similar to the objects instead of using the tag-input as it will make it complex to handle different scenarios and also doesn't play well with the rjsf form
…ieldTemplate for improved workflow editor UI
…rt and improved input handling
…nce and add buildDefaultValuesOfDataSchema utility
… getFieldName utility in widget components
…StepTabs component
…ate for improved form handling and structure
…fault values and improved dirty state management
…plete integration
713c76f
to
d7557d7
Compare
registry={registry} | ||
/> | ||
</span> | ||
<div className="bg-background text-foreground-600 -mt-px ml-auto mr-4 flex items-center gap-1"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a hover state to the collapsible button to be consistent with the add/minus button hover states?
It's generally a good UX practice for all buttons to have a hover state to provide feedback to the user that they are interacting with something (in addition to varying the pointer)
What changed? Why was the change needed?
Screenshots
Screen.Recording.2024-11-25.at.11.56.13.PM.mov
Expand for optional sections
Related enterprise PR
Special notes for your reviewer